First draft of 3.1.1 blogpost #1324
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bishabosha
reviewed
Jan 10, 2022
prolativ
reviewed
Jan 10, 2022
SethTisue
reviewed
Jan 21, 2022
bishabosha
reviewed
Jan 27, 2022
tgodzik
reviewed
Jan 27, 2022
|
|
||
| So, for example, compiling your library using Scala 3.1.2-RC2 with `-Yscala-release:3.0` flag, you make it possible for people still using Scala 3.0 to depend on your library. This has one limitation, you won't be able to use any symbol added to the standard library after 3.0. They are marked in the code and in the documentation by the `@since` annotation that was also added in this version. | ||
|
|
||
| One important note is that the `-Yscala-release` flag is experimental and not yet available in any stable release of the compiler. It means the build tools, such as SBT or Mill, are not yet aware of its existence. Of course, you can declare usage of the flag in your build file, and the compiler will respect it. However, there may still be some hiccups, like generated artifacts depending on the incorrect version of the stdlib. We will do our best to help fix those minor issues before the stable release of 3.1.1. |
There was a problem hiding this comment.
, like generated artifacts depending on the incorrect version of the stdlib
Could you specify exactly why this happens? MAybe potential problems section?
Suggested change
| One important note is that the `-Yscala-release` flag is experimental and not yet available in any stable release of the compiler. It means the build tools, such as SBT or Mill, are not yet aware of its existence. Of course, you can declare usage of the flag in your build file, and the compiler will respect it. However, there may still be some hiccups, like generated artifacts depending on the incorrect version of the stdlib. We will do our best to help fix those minor issues before the stable release of 3.1.1. | |
| One important note is that the `-Yscala-release` flag is experimental and not yet available in any stable release of the compiler. It means the build tools, such as SBT or Mill, are not yet aware of its existence. Of course, you can declare usage of the flag in your build file, and the compiler will respect it. However, there may still be some hiccups, like generated artifacts depending on the incorrect version of the stdlib. We will do our best to help fix those minor issues before the stable release of 3.1.2. |
?
prolativ
reviewed
Jan 28, 2022
Co-authored-by: Jamie Thompson <bishbashboshjt@gmail.com>
Co-authored-by: Tomasz Godzik <tgodzik@users.noreply.github.com> Co-authored-by: Julien Richard-Foy <julien@richard-foy.fr>
Co-authored-by: Michał Pałka <prolativus@gmail.com>
prolativ
reviewed
Feb 1, 2022
|
|
||
| We expect that in the future authors will use the newest available version of the compiler with `-Yscala-release` set to the lowest language version that support all features they need. This way they will be able to benefit from all the bugfixes without restricting their potential audience. | ||
|
|
||
| So, for example, compiling your library using Scala 3.1.2-RC2 with `-Yscala-release:3.0` flag, you make it possible for people still using Scala 3.0 to depend on your library. This has one limitation, you won't be able to use any symbol added to the standard library after 3.0. They are marked in the code and in the documentation by the `@since` annotation that was also added in this version. |
There was a problem hiding this comment.
Actually there are more limitations as described here https://docs.scala-lang.org/scala3/reference/language-versions/binary-compatibility.html
like you cannot depend on libraries compiled for release 3.1 or your code cannot use language features which are not encodable in older TASTy (currently it's not a case but it might be in the future)
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
SethTisue
approved these changes
Feb 1, 2022
prolativ
approved these changes
Feb 1, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Blogpost about 3.1.1 and about the first publicly available version of the compiler with
-Yscala-releaseflag.